Mobile kiosk for intelligent securable devices system

ABSTRACT

A system and method of controlling a securable device may include establishing a centralized data repository with data representative of status of each securable device. Communications with a mobile kiosk executing on a mobile device of a user may be established. Responsive to receiving a request from the mobile kiosk to identify an available securable device local and accessible to the user, the centralized data repository may be accessed, at least one securable device that is available may be identified, and data associated with the identified available securable device(s) may be communicated to the mobile kiosk to cause the mobile kiosk to communicate at least a portion of the data to one of the securable device(s) to provide access thereto. Responsive to receiving a status update of the securable device accessed from the mobile kiosk, the centralized data repository may be updated with the status update.

RELATED APPLICATIONS

This is a Divisional Application of co-pending U.S. patent applicationSer. No. 14/728,887 filed on Jun. 2, 2015, entitled “MOBILE KIOSK FORINTELLIGENT SECURABLE DEVICES SYSTEM,” which claims priority to U.S.Provisional Patent Applications having Serial Nos. 62/006,678, filedJun. 2, 2014 and entitled “INTELLIGENT ACCESS OF ELECTRONIC LOCKS,” and62/006,700, filed Jun. 2, 2014 and entitled “RETROFITTED INTELLIGENT(sic.) ELECTRONIC LOCK,” the contents of which are hereby incorporatedby reference in their entirety.

BACKGROUND

Mechanical lockers are used in both concessional and non-concessionalvenues. In concessional venues, such as airports, bus and trainstations, malls, theme parks, and ski resorts, users generally pay touse the lockers. In non-concessional venues, such as schools and fitnesscenters, users are typically not required to pay to use the lockers.There are a number of problems associated with coin-operated, mechanicallocking systems that require payment or not for use. These problemsinclude the fact that each locker may only accept a limited number ofcoins, and those coins are the only acceptable method of payment.Coin-operated lockers require the user to access lockers with a separatekey, issued upon purchase of the locker. As a result, a third-party mustcollect the coins from the system and the vendor/owner cannot alwaysaccount for the correct amount of money. Another problem with mechanicallockers is that keys must be used to operate them. These keys arecommonly lost or stolen, thereby creating maintenance and securityproblems. For non-concessional venues, users generally bring their ownkeys and locks to use the services of locker storage. Many times, usersforget to bring their keys or locks or forget the passcode to regainaccess into occupied lockers, resulting in further complications andissues.

Electronic locker systems are typically configured the same manner,where each system includes multiple lockable storage enclosures, acontroller unit that often includes a personal computer (PC) or othercomputing device, electronic locks, and a credit card reader or a cashdepository to enable users to rent the lockable storage enclosures. Theelectronic locker systems also include power systems, cabling,electronic drivers, ticket printers, user interfaces (e.g., touchscreen), and so on. Electronic locker companies compete for new businessby entering into revenue sharing business arrangements because, in mostcases, the cost of electronic lockers is too expensive for venues topurchase and because the venues typically do not want to be responsiblefor or are ill-equipped to handle maintenance of the electronic lockersystems. As understood in the art, the most complicated and expensivemanufacturing and assembly costs are the controller unit and powercomponents.

SUMMARY

Disclosed herein are embodiments of methods and systems for operating“smart lockers” and other securable devices using a mobile kiosk,thereby reducing the complications and cost of conventional kiosks orcontroller units and supporting electronics and power components. Thesmart lockers may include local, non-networked locking devicesconfigured to secure a securable device (e.g., locker). The use of amobile kiosk may be applied to concessional and non-concessional storageunits (e.g., lockers) that may hold any items for temporary or permanentstorage. The mobile kiosk may be configured by a combination of softwareexecuted on a mobile device, such as a smartphone, that may operate inconjunction with a remote management server, such as a management serveroperating in the “cloud” and accessible to the mobile device via acommunications network.

The mobile kiosk may use inherent technologies of mobile devices thatprovide for short-range and long-range communications paths andprotocols. The short-range or local communications protocols may includea set of wireless technologies including, but not limited to, Bluetooth,smart Bluetooth, WiFi, NFC, Zigbee, RFID, or any other localcommunications protocol to communicate with smart lockers. Thelong-range communications protocols may include conventionaltelecommunications protocols, such as GSM, CDMA, or other wirelesscommunications protocol.

Through use of a mobile kiosk, a user may be able to rent a smart locker(or other securable device) via a mobile device in conjunction with aremote management server via a long-range communications protocol, andthe mobile kiosk may communicate with a selected or assigned smartlocker via a short-range communications protocol. By configuring smartlockers to interface with mobile kiosks, the complexity and expense of aconventional kiosk and supporting electronics and cabling may be reducedor eliminated. The mobile kiosk may enable the user, after renting asmart locker, to lock and unlock the smart locker via the mobile kioskor be independent of the mobile kiosk depending on the configuration ofthe user interface of the smart locker. In one embodiment, the user canuse a mobile device or the mobile kiosk to directly communicate withindividual smart lockers as opposed to the smart lockers communicatingdirectly with a central control kiosk. Using mobile kiosks allows usersto not only unlock and lock the smart lockers, but also view usagehistory, pay for rental, share access with other users, and reserve thesmart lockers.

In a configuration in which a local, mobile kiosk may be fixedlypositioned and associated with a smart locker system, payment hardwaremay include, but not be limited to, credit card readers, NFC readers orEMV readers. In one embodiment, rather than using conventional paymentmethods, other online payment methods may be employed, such as throughpayment services, such as PayPal®, Apple Pay®, or other online paymentservice in which the mobile kiosk (e.g., smart phone or tablet)capabilities are used to eliminate the need for a hardware device at thelockers. Other apps or online applications (e.g., websites) that enablecard payment methods may be utilized. The local, mobile kiosk operatingon a tablet or other monitor that is wirelessly in communication withthe smart lockers enables a user to control access to the smart lockers.In one embodiment, individual smart lockers are outfitted with anembedded printed circuit board in conjunction with an electronicallycontrolled lock that acts as a locker controller. The locker controllermay include, but not be limited to, a number of components, such asillumination device (e.g., LED), communications modules (e.g., Bluetoothmodule, WiFi module), GPS circuit, network interface, alarm sensor,processing unit, and local sensor (e.g., NFC radio, RFID reader). Inanother embodiment, the locker controllers may be connected wirelesslyor wired (daisy chained) to a “mother” smart locker controller thathandles the unlocking/locking commands to a plurality of smart lockers.

One embodiment of a securable device within a set of securable devicesthat enable users to secure items may include a computing unit, a memoryunit in communication with the computing unit, a charge device incommunication with the computing unit and the memory unit, a short-rangecommunications device in communication with the computing unit, andconfigured to communicate a short-range wireless communicationsprotocol, and an electromechanical lock device in communication with thecomputing unit. The short-range communications device may be configuredto enable a user operating a mobile kiosk on a mobile device capable ofcommunicating using the short-range communications protocol tocommunicate data with the computing unit. The computing unit may beconfigured to process data received from the mobile device. Responsiveto determining that the data is addressed to the securable device fromamong the set securable devices, the computing unit may be configured to(i) process the data to control the electromechanical lock device of thesecurable device and (ii) update status data of the securable device.Status data may be communicated via the short-range communicationsprotocol to the mobile kiosk to cause the mobile kiosk to update a datarepository inclusive of status data of the set of securable devices withthe status data of the securable device.

One embodiment of a method of controlling a securable device in a set ofsecurable devices may include establishing a centralized data repositorywith data representative of status of each securable device in the setof securable devices. Communications with a mobile kiosk executing on amobile device of a user may be established. Responsive to receiving arequest from the mobile kiosk to identify an available securable devicelocal and accessible to the user, the centralized data repository may beaccessed, at least one securable device that is available may beidentified, and data associated with the identified available securabledevice(s) may be communicated to the mobile kiosk to cause the mobilekiosk to communicate at least a portion of the data to one of thesecurable device(s) to enable the user to access the securable device.Responsive to receiving a status update of the securable device accessedby the user from the mobile kiosk, the centralized data repository maybe updated with the status update of the associated securable device.

One embodiment of a mobile kiosk may include machine-readableinstructions configured to execute on a mobile device, and, when themachine-readable instructions are executed by the mobile device, causethe mobile device to communicate a request via a long-distancecommunications path to a management server, where the request mayinclude an identifier associated with multiple securable devices.Responsive to one of the securable devices being assigned to a user ofthe mobile kiosk, a control signal may be communicated via a localcommunications path with the assigned securable device, where thecontrol signal may cause the securable device to transition from alocked state to an unlocked state. Responsive to receiving a statusupdate from the securable device via the local communications path ofthe securable device transitioning from the locked state to the unlockedstate, the status update of the securable device may be communicated viathe long-distance communications path to the management server.

One embodiment of a process of controlling an electromechanical lockthat is electronically controlled may include establishing, by acommunications device associated with the electromechanical lock, alocal communications link with a mobile device. The electromechanicallock may be responsive to a control signal including a networkidentifier. In response to receiving a control signal via the localcommunications path, the control signal may cause the securable deviceto transition between a locked state and an unlocked state. In responseto the electromechanical lock transitioning between the locked state andthe unlocked state, a status update may be communicated via the localcommunications path of the securable device transitioning between thelocked state and the unlocked state.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present invention are described indetail below with reference to the attached drawing figures, which areincorporated by reference herein and wherein:

FIG. 1 is an illustration of an illustrative smart electronic lockersystem configured to be accessed via mobile kiosks;

FIG. 2A is an illustration of an illustrative smart locker systemenvironment that utilizes mobile kiosks for accessing smart lockers;

FIG. 2B is an illustration of a high-level view of a mobile deviceconfigured as a mobile kiosk that operates to communicate with a smartlocker and a cloud-based management server or controller;

FIG. 3 is an illustration of an illustrative locker computer device andassociated electronics that enables the locker computer device toprovide for a “smart locker;”

FIG. 4 is an illustration of an illustrative mobile device configured tooperate as a mobile kiosk for controlling smart lockers;

FIG. 5 is an illustration of an illustrative management serverconfigured to communicate with mobile kiosks to manage lockers in asmart locker system;

FIG. 6 is a flow diagram of an illustrative high-level process for auser to secure or withdraw items smart locker or access other securabledevices configured with a smart lock;

FIG. 7A is an interaction diagram of an illustrative environment inwhich communications between the mobile kiosk (FIG. 2A), cloudmanagement server, and electronic lock may enable a user of the mobilekiosk to rent a securable device;

FIG. 7B is an interaction diagram of an illustrative environment inwhich communications between the mobile kiosk, cloud management server,and electronic lock may enable a user of the mobile kiosk to performsecond actions (e.g., extend rental, end rental) with a rented securabledevice;

FIGS. 8A-8C are screenshots of illustrative user interfaces that supportprocesses for establishing a new rental, extending rental, and endingrental processes of securable devices, respectively; and

FIGS. 9A-9C are screenshots of illustrative user interfaces that areparticular for renting mobility devices utilizing a mobile kiosk.

DETAILED DESCRIPTION

With regard to FIG. 1 an illustration of an illustrative “smart”electronic locker system 100 configured to be accessed via mobile kiosks102 a-102 n (collectively 102) being operated by users 104 a-104 n(collectively 104) is shown. The mobile kiosks 102 may be configured asmachine-readable instructions (e.g., mobile app, website on a mobilebrowser) being executed by a mobile device, such as a smart phone. Theelectronic locker system 100 may include multiple electronic lockers or“smart lockers” 106 a-106 n (collectively 106) that includeelectronically controlled locks or “smart locks” 108 a-108 n(collectively 108). Each of the smart locks 108 may be configured with awireless transceiver, processing unit, memory, motor driver, battery orcharge device for an electromechanical lock, as understood in the art.The smart locks 108 may be non-networked devices in that there is nolocal, hardwired kiosk with which the smart locks 108 communicate. Byusing mobile kiosks 102 operating on mobile devices of users 104, thesmart locks 108 may be accessible by the users 104, thereby eliminatingthe complexity and costs typically associated with conventional kiosksthat are generally hardwired to the electronic locks of lockers. In oneembodiment, a battery of the smart lock may be charged using a solarpanel or other energy collection and conversion device, such as wirelesspower. In alternative embodiments, the “smart locks” 108 may beconfigured as individual locking structures that may secure variousitems, such as mobility devices (e.g., bicycles, scooters, etc.), safeswithin hotel rooms or elsewhere, or any other item that may be securedby a smart lock that operates in the same or similar manner as smartlocks 108 when operating within the smart lockers 106.

The electronic locker system 100 may be configured with individualelectronic lockers 106 that serve as temporary storage for personalitems in indoor or outdoor venues. In an alternative embodiment, theindividual electronic lockers 106 may be operated by delivery servicesto deliver packages or other items for customers to pick up at thelockers 106. In such a delivery service configuration, the service mayassign a locker 106 a to a user, and the user may use a mobile kiosk114.

In one embodiment, a mobile kiosk 114 may be configured in the form of amobile device, such as a tablet, held and operated by an operator orattendant, but possibly fixedly positioned for security reasons. Themobile kiosk 114 may be in local communication range of the electroniclocker system 100 so that a local wireless communications protocol, suchas Bluetooth or WiFi, may be utilized to communicate with and,optionally, control operation of the smart locks 108. The mobile kiosk114 may be configured to function the same or similar to operation ofthe mobile kiosks 102, as further described hereinbelow. In oneembodiment, the mobile kiosk 114 may be fixedly positioned by a mountingbracket 116 onto a wall (not shown) or a panel of the electronic lockersystem 100. In an alternative embodiment, the mobile kiosk 114 may becarried by an operator to assist users to rent or otherwise access theelectronic lockers 106 or other devices (e.g., mobility devices) thatare secured by smart locks. In one embodiment, the mobile kiosk 118 mayinclude a payment processor 118 that is a credit or debit card reader orEuropay, MasterCard, and Visa (EMV) reader to read integrated circuitcards (“chip cards”) that enables a user to swipe or otherwise read acredit card or debit card, among other ways for payments to be made bythe users 104. For example, the payment processor 118 may include a nearfield communication (NFC) circuit that may enable a user to pay via a“tap” of his or her mobile phone with NFC payment capability using amobile wallet, as understood in the art. Alternative payment methods,such as PayPal®, Apple Pay, Android Pay, or other payment methods may beutilized.

The smart lockers 106 may include front doors 120 a-120 n (collectively120) on which the smart locks 108 are respectively secured, and used tosecure goods within the smart lockers 106. In one embodiment, as shownwithin a compartment 122 of smart locker 106 c, a button or other userinteractive electronic device 124 may enable an operator operate tocause a signal to be sent via a mobile device, such as mobile kiosk 114to provision the smart locker 106 c in the electronic locker system 100to be recognized and, optionally, assigned an identifier (ID). Thebutton 124 may be temporarily or fixedly positioned. Alternatively,rather than using a button 124, a sticker or other non-electronicindicia inclusive of a unique identifier associated with respectivesmart lockers 106 may be used and scanned or otherwise utilized by anelectronic device, including the respective smart locks or provisioningmobile device to provision each smart locker. In yet another embodiment,an RFID tag or NFC tag may be positioned within each of the smartlockers 106 to provide for provisioning of the smart lockers 106. Acommunication that includes a unique identifier generated by the buttonor non-electronic indicia to a management server enables the server toquickly be provisioned.

Utilizing the button 124 and provisioning process enables use of anylockers or securable device, regardless of size, to be installedflexibly and more efficiently. In one embodiment, the smart locks 108may receive or generate a signal inclusive of an identifier created oridentified by the button, sticker, electronic tag, or otherwise, andcommunicate the identifier to a management server via the mobile kiosks102, for example. In another embodiment, the smart locks 108 maycommunicate a network address, such as an IP address, MAC address, orother network address, along with the unique identifier (or otherinformation, such as name of physical location) to the management server210 via the mobile kiosks 102.

As previously described, the mobile kiosks 102 may be mobile devices,such as smart phones, configured to execute instructions in the form ofa mobile app or website that integrates with various features of themobile devices. The mobile kiosks 102 may operate as a communicationbridge for a management server (see, for example, FIG. 2A) executing ona communications network, such as the Internet, to enable users 104 toaccess the smart lockers 106. In one embodiment, the mobile kiosks 102may enable (i) confirmation code(s) to be communicated via text, email,or other communication protocol, (ii) receipts to electronicallycommunicated to the mobile device, (iii) short-range communications(e.g., NFC, Bluetooth) to be used to unlock/lock a smart locker that hasbeen rented by communicating with (e.g., “tapping” an NFC reader 112 a)to communicate a verification code with or without presentment to theuser, (iv) locking and unlocking a smart locker by using RFIDcommunications with a passive RFID reader to communicate a lock andunlock code, for example, (iv) communication of instructions to a user,(v) imaging an indicia associated with a smart locker using a camerafeature rather than having to enter an indicia (e.g., locker number)into a text field or otherwise, (v) usage (e.g., lock, unlock, dooropen, door close) verification of a smart lock and locker door to becommunicated via the mobile kiosk to the management server, and soforth.

The mobile kiosks 102 may further be configured to provide status ofsome or all of the smart lockers 106 in the system within a given region(e.g., locker bank, section of an amusement park, building), purchasetemporary rental duration, reserve lockers remotely, viewcharacteristics (e.g., size) of lockers, and unlock/lock lockers througha mobile device. The mobile kiosks 102 may also provide for statusnotifications of the smart lockers 106, where the status notificationsmay include duration of time that each of the smart lockers 106 haveremaining for current rentals, notice when a smart locker becomesavailable in response to a user releasing the locker, add a name andother information (e.g., telephone number) to a queue for the smartlockers 106 for notification of an available locker, and so on.

To assist users in the transactions of the electronic locker system 100,a PCB board (not shown) may be used within each of the smart lockers 106of the electronic locker system 100, selectably connected wirelessly viaa local communications protocol to the mobile kiosks 102, and/orconnected wirelessly to the mobile kiosk 114. The mobile kiosks 102 mayprovide for payment via a user interface (not shown) via the managementserver or other remote payment system, and the mobile kiosk 114 mayinclude the payment processor 118, as previously described. The mobilekiosk 114 may also be configured to enable a user to operate pay for andinterface with the smart lockers in the same manner as provided by themobile kiosks 102 being operated by mobile devices of the users 104. Byproviding a simple tablet for consumers to rent lockers and/or accesslockers, a user who stores his or her mobile device (and mobile kiosk)in a locker can later unlock the locker using the mobile kiosk 114. Inan alternative configuration, the smart lockers 106 may include a keypadthat may be used by the user to lock and unlock the respective smartlocks 108.

With regard to FIG. 2A, an illustration of an illustrative smart lockersystem environment 200 that utilizes mobile kiosks 202 a-202 n(collectively 202) for accessing smart lockers 204 a-204 n (collectively204) is shown. The smart lockers 204 are shown to include respectiveelectronic or electromechanical locks 206 a-206 n (collectively 206) andcorresponding locker computer devices 208 a-208 n (collectively 208).The electromechanical locks 206 may be slave devices to respectivelocker computer devices 208, which operate as master devices, thatcontrol operation of the respective electronic locks 206.

As shown, the smart locker system environment 200 includes a managementserver 210 that operates as a central controller or repository withwhich the local kiosks 202 communicate via communications network 212when a user is seeking to rent or otherwise interact with a smart locker204. In communicating with the management server 210, the mobile kiosks202 use a long-range communications channel or path 216 that utilizes along-range communications protocol, such as a mobile communicationschannel and protocol, as understood in the art via mobile communicationsnetwork equipment 214. Between the mobile kiosks 202 and locker computerdevice(s) 208, a local communications channel (e.g., Bluetooth) 218 maybe established and a local communications protocol may be utilized.

With regard to FIG. 2B, an illustration of a high-level view of a mobiledevice configured as a mobile kiosk 202 a that operates to communicatewith a smart locker 204 a that is non-networked and a cloud-basedmanagement server or controller 210 is shown. The mobile kiosk 202 aprovides for a communications bridge between the management server 210and smart lock 206 a of the smart locker 204 a. The mobile kiosk 202 amay be configured using a mobile app or by providing access to a webpageusing a web browser, for example.

In one embodiment, a user may be able to reserve one of the smartlockers 204 prior to visiting a locker facility using a desktop orlaptop computer 202 o or a mobile kiosk 202 a, where the mobile kiosk202 a would reserve one of the smart lockers 204 or other securabledevice via a management server without having to be in localcommunication proximity with the smart lockers 204. Thereafter, the usermay become in local communication with the smart lockers 204 with themobile kiosk 202, to initiate a rental period.

In serving as a communications bridge, the mobile kiosk 202 a mayprovide limited kiosk functionality, such as providing a user interfacethat enables a user (i) to select a locker type and term of rental, (ii)to enable a user to pay for the rental, (iii) to select a PIN to lockand unlock the smart lock 206 a, and (iv) to provide communicationsbridge functionality utilizing long-range and short-range communicationsprotocols between the smart lock 206 a and management server 210 toenable the management server 210 to perform the remainder of the kioskfunctions. As a bridge, the mobile kiosk 202 a may enable a smart locker204 a to communicate status updates via the mobile kiosk 202 a, wherestatus updates may include, but not be limited to, lockercharacteristics, time stamps, physical location (geographic locationand/or position within a locker bank), lock status, RFID status, NFCstatus, LED status, Bluetooth status, door status (e.g., opened/closed),or any other information indicative of status of the smart locker 204 a.The locker computer device 220 may receive a request to unlock a lockerfrom a mobile kiosk using a short-range communications protocol. Therequest may include a code, such as a 4-digit PIN, and the lockercomputer device 208 a may verify the code before unlocking. In oneembodiment, the smart locker 204 a may include a keypad 222 thatoperates as a user interface for the user to enter the PIN previouslydownloaded via the mobile kiosk 202 a, thereby allowing the user tostore the mobile kiosk 202 a (i.e., mobile device on which a mobilekiosk app is operating) in the smart locker 204 a, while still allowingfor the user to unlock the smart locker 204 a.

A variety of different options for controlling the smart locks 206 maybe utilized. As an example, the PIN may be a code that the user enters.However, other options for creating or selecting a PIN may be utilized,including assigning a PIN to the user, using a unique mobile device ID(e.g., subscriber identity module (SIM), mobile identification number(MIN)), using a user account number, or using another identifier. In oneembodiment, the user may not be issued the PIN and the management servermay communicate the PIN along with a network address or other identifierof the smart lock via the mobile kiosk that, in turn, communicates thePIN to the smart lock. Alternative ways of providing a user with a PINmay be utilized.

In providing for a substantial kiosk functions, the mobile kiosk 202 amay be configured (i) to store available lockers at a locker bank fromdata received from the management server and/or data collected by themobile kiosk 202 a (e.g., polling status from each of the smart lockers204), (ii) to enable a user to select a locker type and term of rentalto rent the smart locker 204 a, (iii) to select a locker to assign tothe user, (iv) to determine a PIN or enable a user to submit a PIN tolock and unlock the smart locker 204 a, (v) to receive and store lockerstatus information, (vi) to receiving status update information of allof the locally available lockers from the management server 210 toenable the mobile kiosk 202 a to operate relatively autonomously orindependent of the management server in a distributed kiosk managementconfiguration, which is operating as a central controller for at least aportion of locker banks being managed by an operator.

As a result of providing more significant kiosk features in the mobilekiosk, if the lockers (or other securable devices) are positioned in ageographic location in which no or limited mobile communications areavailable, then users with a mobile kiosk app may still be able toutilize the lockers. That is, if the mobile device is out-of-range orhave no or weak communications signaling with a mobile communicationsnetwork or even WiFi network, then a user with a mobile kiosk still maybe able to rent a locker. In one embodiment, the user may have to have avalid credit card, debit card, prepaid card, or other approved paymentmeans pre-approved by an operator as the mobile kiosk may update therental information after the rental transaction is complete. In oneembodiment, a stand-alone device, such as a room safe, may operate by amobile kiosk communicatively connecting to a smart lock of thestand-alone device so as to receive status from the lock. The mobilekiosk could be preloaded with payment, an application capable ofself-managing a transaction, or other information that allows for themobile kiosk to perform a rental transaction independent of themanagement server if the mobile device on which the mobile kiosk isoperating is out of range of a cellular or Internet connection orotherwise prevented from communicating with the management server.

With regard to FIG. 3, an illustration of an illustrative lockercomputer device 300 and associated electronics, at least in part,enables the locker computer device 300 to provide for a “smart locker”is shown. In one embodiment, the locker computer device 300 andassociated electronics may include a printed circuit board (PCB),wiring, and other electronic devices. The locker computer device 300 mayinclude a processing unit 302 that executes software 304. The software304 may facilitate locking and unlocking a locker in response toverifying a code and/or other information. The processing unit 302 maybe in communication with a memory 306 and input/output (I/O) unit 308for communicating with sensors, network communications devices, if notincorporated into the I/O unit 308, and the like.

The locker computer device 300 may be in communication with a number ofdevices, including an illumination device 310, such as a light emittingdiode (LED), that may be used to indicate lock/unlock status and otherstatuses of other conditions. In one embodiment, the illumination device310 may include multiple illumination devices, where two LEDs mayproduce the following indicators as shown in TABLE I:

TABLE I Indicators of Illumination Devices LED 1 INDICATORS LED 2INDICATORS Green - unrented Green - unlocked Red - rented Red - lockedFlashing White - waiting for RFID No light - out of service or lightfailure Flashing green - rental extended; door open or unlocked

It should be understood that additional and/or alternative number ofLEDs that produce the same or different indicators may be used. Abattery source 312, such as a lithium ion battery or rechargeablebattery along with a photovoltaic device, may be used to power thelocker computer device 300. A lock bolt sensor 314 may be used to senseposition of a lock bolt of a securable device, such as an electroniclocker. A Bluetooth chip 316 may be used to enable the locker computerdevice 300 to communicate with a mobile device using a Bluetoothcommunications protocol, as understood in the art. A tamper sensor 318,such as motion and/or light sensor, may be configured to sense whether asecurable device is tampered with while the securable device is in alocked state. A control reset 320 may be configured to enable anoperator to perform a “hard” reset of the locker computer device 300during maintenance or resetting due to an error condition.

A solenoid 322 may be an electromechanical mechanism that may be engagedand disengaged to lock a securable device in response to the lockercomputer device 300 applying and removing an electric charge. An alarmsensor 324 may be configured to sense an action, such as a locker doorbeing opened when the locker computer device 300 is in a lock state. AnNFC radio 326 may be configured to communicate with another NFC device,such as a mobile device configured with an NFC radio, for use inexchanging a lock/unlock code, access code, payment code, personalinformation, mobile device information, or otherwise. It should beunderstood that the configuration shown is illustrative and thatadditional and/or alternative configurations may be utilized. Forexample, the components may include additional, alternative, or fewersensors. In one embodiment, a passive RFID reader may be included withthe locker computer device 300 for reading RFID signals of RFID signalgenerators that may be used to unlock and lock the securable device.Still yet, some of the components shown may be integrated into thelocker computer device 300 or positioned on a PCB of the locker computerdevice 300.

In operation, the locker computer device 300 may update a local datastructure stored in the memory 306 that indicates whether the locker isavailable based on a lock status of the locker. The locker computerdevice 300 may also transmit, to a management server 200 (FIG. 2A), amessage indicating that the locker has been unlocked and locked. Thelocker computer device 300 may also include transmitting via theBluetooth chip 316 to a mobile kiosk operating on a mobile device thatwas used to rent the locker updates of information (e.g., lock status,door position status, alarm status, or otherwise) processed by thelocker computer device 300. The NFC radio 326, which may alternativelybe a passive NFC reader, may receive NFC actions from a mobile devicethat includes an NFC radio. In one embodiment, a passive RFID reader(not shown) may receive a signal to turn on after a button has beenpressed on a keypad (not shown) to “wake up” the passive RFID reader.The mobile kiosk may be configured to utilize a local communicationschannel as desired by the user.

In one embodiment, the locker computer device 300 may contains one ormore printed circuit boards (PCBs) with circuitry and electroniccomponents that provide for a variety of functions and features, such asthose shown in FIG. 3. The locker computer device 300 may be configuredto communicate signals to an electronic lock 206 a (FIG. 2A), forexample, to either lock or unlock the smart locker 204 a. The PCBs maybe installed in an individual locker and communicate with a mobile kioskwhen communicating with the management server 210 (FIG. 2A). In oneembodiment, individual PCB boards may be installed in lockers and bedaisy chained to a “motherboard,” where the motherboard includescomponents, such as those shown in FIG. 3.

With regard to FIG. 4, an illustration of an illustrative mobile device400 configured to operate as a mobile kiosk for controlling smartlockers is shown. The mobile device 400 is shown to include a processor402 that executes software 403. The processor 402 may be incommunication with an input/output (I/O) unit 404, NFC radio 406,Bluetooth chip 408, and a number of other electronic devices, such as anelectronic display, as understood in the art. The software 403 may beconfigured to execute a mobile kiosk app, as understood in the art, thatmay be configured to cause the mobile device 400 to become a mobilekiosk, as further described herein. The mobile kiosk application, whichessentially converts the mobile device into a mobile kiosk that operatesas a bridge between one or more smart lockers and a management serverlocated on a communications network as described with regard to FIG. 2A,may be utilized by a user of the mobile device 400. Rather than being anapp, a website that may be operated by a mobile browser mayalternatively be utilized.

The processor 402 may further be in communication with a memory 410 thatis configured to store software and data associated with the mobilekiosk. As shown, the memory 410 may be configured to store a mobilekiosk app module 412 that, when executed by the processor 402, createsand manages data used to support the mobile kiosk module 412. The datamay include a number of different data elements that are used by themobile kiosk to control or otherwise manage or track operation of themobile kiosk app module 412 when accessing or controlling individualsmart lockers. The data may include, but not be limited to,password/codes 414 (e.g., 4-digit personal identification number (PIN)),reserved locker commands 416, preferences 418 (e.g., short-rangecommunications preferences), account profile 420, history 422, andtamper message 424. Each of the data elements 414-424 may be particularto a user of the mobile device who desires to or has rented securabledevices, such as smart lockers. In one embodiment, the mobile kiosk appsmodule 412 may be configured to display some or all of the data elements414-424 to the user via a user interface module 426 that generates oneor more graphical user interfaces for the user to utilize in accessingand controlling the securable devices.

The software 403 being executed by the processor 402 may further beconfigured to execute a locker bank module 428 that operates to trackdata and/or information associated with one or more locker banks withwhich the mobile device 400 may communicate. The locker bank module 428may operate to store and retrieve data being stored in the memory 410,where the data may include status of lockers data 430, physicallocations of lockers 432, and queue for lockers 434. The status oflockers data 430 may include a list or matrix of status identifiers asto whether lockers within a locker bank or otherwise are available orcurrently being rented. The status of lockers data 430 may also includetimers associated with each of the lockers that are currently beingrented, so that a user may view the timers to determine when aparticular locker or any locker within a locker bank will becomeavailable. The physical locations of lockers 432 may list a geographiclocation of locker banks to assist a user of the mobile device 400 todetermine where he or she may find an available locker. The queue forlockers data 434 may enable a user to be listed in a queue for a nextavailable locker within a locker bank. In one embodiment, the queue forlockers data 434 may show a list of a number of different people waitingfor lockers at a particular locker bank or within a geographic area. Inone embodiment, the locker bank module 428 may be configured toautomatically notify the user of the mobile device 400 when a nextlocker is to become available and an approximate time of theavailability. Additional and/or alternative data may be associated withthe locker bank module 428 to assist the mobile kiosk app module 412 inmanaging locker banks.

In operation, the mobile kiosk app module 412 may be configured toprovide a number of different access and control functions, includingunlock/lock commands that are communicated to a smart locker to unlockand lock the smart locker, locker reservation commands, passwords/codesfunction that enables the user to create or alter passwords or codesthat are used to lock and unlock a smart locker, or otherwise. Theaccess and control functions may be accessible via a user interface thatis managed by the user interface module 426. The user interface module426 may provide for alternative and/or additional functionality used onaccessing and controlling individual smart lockers or securable devicesalong with providing functions associated with locker banks (e.g.,managing a queue, status of lockers within a locker bank or geographicregion with multiple locker banks).

With regard to FIG. 5, an illustration of an illustrative managementserver 500 configured to communicate with mobile kiosks (not shown) tomanage lockers in a smart locker system is shown. The management server500 may be the same or similar to the management server 200 shown inFIG. 2A. The management server 500 may be implemented as or within aserver farm including multiple machines as opposed to a single server.As shown, the management server 500 may include a processor 502 thatexecutes software 504, input/output unit 506 used to communicate dataover a communications network (not shown), and memory 508 configured tostore one or more databases. The I/O unit 506 may include one or morenetwork interface cards (NICs), as understood in the art. Asillustrated, the memory 508 may include a locker application database510, an advertising database 512, a mobile database 514, and apre-assigned database 518.

The locker application database 510 may store information, such as userpin codes, passwords, usage data, access records, pricing algorithms,and RFID codes. The information stored in the locker applicationdatabase 510 may be encrypted and received from mobile kiosks, and maybe used to ensure that the mobile kiosks that are being used to accessor near smart lockers are synchronized. An advertising database 512 maybe configured to store advertisements paid by third-party advertisers,and the advertisements may be communicated to mobile kiosks operating onmobile devices of users when using the mobile kiosk app or website. Themobile database 514 may store any information that is input into amobile device by a user operating a mobile kiosk, where such informationmay include encrypted payment information, account details, rentalhistory, and the like.

Although not limited by any particular theory of operation, in certainembodiments, the management server 500 may be configured to enable themobile kiosks to access one of multiple lockers by the management server500 being programmed to synchronize to an existing pre-assigned database518 of stored user information, associating that stored profile to auser with one of the locker(s) so that the user is authorized to accessthe assigned locker. The pre-assignment process allows for an extralayer of authentication that is directly associated with the location orfacility that the electronic locker system 100 is positioned. In oneexample, a user may enter his or her flight confirmation number into amobile kiosk to unlock/lock one of the lockers smart lockers availableto the mobile kiosk. By providing the flight confirmation number, theTSA and airport security can ensure that a user's belongings are storedwhile present at an airport. Thus, the system ensures that the depositorof an item in a smart locker is also the recipient. Utilizing the smartlocker system described herein, the user can rent a smart locker througha mobile kiosk using a smart phone or tablet.

With regard to FIG. 6, a flow diagram of an illustrative high-levelprocess 600 for a user to secure or withdraw items from a smart lockeror access other securable devices configured with a smart lock is shown.The process 600 provides an example of a user flow using either a mobilekiosk operating from a personal mobile device or a tablet that may beavailable at the securable devices that is determined by the user atstep 602. At step 604, a user may launch a mobile kiosk app or access awebsite that provides the same or similar functionality as a mobilekiosk app. If the user has not already signed up for an account orotherwise registered with a mobile kiosk and/or management server, theuser may be requested to enter payment information into the mobileapplication to enable locker access via the mobile kiosk. At step 606, auser may request access to a smart locker via the mobile kiosk. In oneembodiment, the mobile kiosk communicates the request to a managementserver, and, upon verification by the management server, sends alock/unlock command to the smart locker. At step 608, an electronic lockof the smart locker receives an unlock signal to cause the electroniclock to transition from a locked state to an unlocked state. After auser deposits or withdraws items from the smart locker or otherwiseaccess the smart locker, the locker computer device may communicate astatus signal to the mobile kiosk to update a data structure at themobile device and/or at the management server via the mobile deviceoperating the mobile kiosk app. The status signal may include alock/unlock state signal, door open/close signal, locker empty signal(if a compartment sensor exists at the smart locker), or any otherstatus signal.

As an alternative to the user utilizing a mobile kiosk app on a mobiledevice, the user may use a tablet or LCD monitor at step 614. In oneembodiment, a PIN code or password used to access the smart locker froma mobile device may be stored in the management server, and in the casethat the mobile device is not accessible (e.g., because the mobiledevice is in the smart locker), the PIN code or password may beaccessible via the tablet. At step 616, the locker computer device, suchas a tablet, may recognize a rental code (e.g., PIN code) or password,and the electronic lock receives an unlock signal via the tablet at step618 to cause the electronic lock to transition from a lock state to anunlock state. At step 620, the user may access, store, or withdraw itemsfrom the smart locker. At step 622, the smart locker may communicatestatus data to the mobile kiosk, in this locker computer device, tocause the mobile kiosk to update data records and/or communicate thestatus data of the smart locker to the management server to updaterecords being managed thereby.

With regard to FIG. 7A, an interaction diagram of an illustrativeenvironment 700 a in which communications between the mobile kiosk 202 a(FIG. 2A), cloud management server 210, and electronic lock 206 a of asmart locker 204 a enable a user of the mobile kiosk 202 a to rent asmart locker is shown. The environment 700 a is shown to include anillustrative process 702 that starts at step 704 at the mobile kiosk 202a. At step 706, the mobile kiosk 202 a may receive a site ID or locationat which securable devices are located. In receiving a site ID, themobile kiosk 202 a may use a camera or other electronic sensor of amobile device on which the mobile kiosk 202 a is operating to image a QRcode or other indicia, interface with an NFC tag, communicating using ashort-range communications path that includes an indicia or signal of aphysical address, network address, or other ID type from the smartlocker, and connect with the cloud management server 210 via acommunications network. In an alternative embodiment, the QR code orother indicia may direct the mobile device to a network address thatenables a mobile app configured as the mobile kiosk 202 a to bedownloaded to the mobile device. In connecting with the cloud managementserver 210, a mobile device may access a website or mobile app eachconfigured to operate as a mobile kiosk, and execute machine-readableinstructions to communicate information to the cloud management server210. At step 708, the mobile kiosk 202 a may receive a request from auser to perform a first action, in this case, to rent a lock. At step710, the mobile kiosk 202 a communicates a query to the cloud managementserver 210 to perform a search in a site database inclusive ofinformation associated with locks associated with the site ID. At step712, the cloud management server 210 may identify available locks andrental information associated with the available locks from the sitedatabase for presentment to the user of the mobile kiosk 202 a.

At step 714, the user may view the available locks and rentalinformation, and select a lock and rental term, where the rental termmay include an amount of time (e.g., two hours, four hours, full day,etc.) for which the user desires to rent the lock. At step 716, the usermay make a secured payment to rent the selected lock for the selectedrental term, and communicate a request for the lock rental to the cloudmanagement server 210 to make a payment based on the desired lock andrental term. It should be understood that renting a lock may includerenting a lock associated with a locker system, mobility device, orother securable device. The payment may be managed by the cloudmanagement server 210 at step 718. Once payment has been approved andverified by the cloud management server 210, at step 720, the cloudmanagement server 210 may assign a lock to the user and communicate aunique lock ID to the mobile kiosk 202 a. In response to receiving theassigned lock and unique lock ID from the cloud management server 210,the mobile kiosk 202 a may communicate with the smart lock 206 autilizing the lock ID and communicate an action, such as “open” or“unlock.”

In response to the smart lock 206 a receiving the unique lock ID and“open” or “unlock” action request, the smart lock 206 a may unlock atstep 724 to enable the user of the mobile kiosk 202 a open the smartlock 206 a and store, remove, or otherwise access his or her belongingsin the case of the lock being positioned on a locker. At step 726, theuser may close and lock the smart lock 206 a utilizing a user interface(e.g., keypad) in communication with the smart lock 206 a, and the smartlock 206 a may communicate to the mobile kiosk 202 a an updated status,such as “rental initiated,” “locked,” and/or other status update. Themobile kiosk 202 a, may, in return, communicate the status of the smartlock 206 a to the cloud management server 210, which, in response toreceiving the updated smart lock 206 a status, update the site database.By using the cloud management server 210 to operate as a centralcontroller for all mobile kiosks 202 (FIG. 2A), multiple mobile kiosksmay be utilized, and accurate knowledge of lock availability may beprovided.

It should be understood, however, that alternative configurations of theillustrative process 702 may be provided. For example, the mobile kiosk202 a may notify the cloud management server 210 of its geographiclocation, and the cloud management server 210 may communicate data ofthe smart lock 206 a at or near the mobile kiosk 202 a so that themobile kiosk 202 a may provide a unique lock ID independent of the cloudmanagement server 210.

As a result of utilizing smart lockers that are non-networked, such asbeing networked in a cluster of networked lockers, rather than anoperating having to utilize locker bank configurations that areconfigured in rows or columns, alternative configurations of lockers maybe utilized. For example, individual lockers may be attached to a bankof lockers or otherwise place in close proximity as wiring harnesses andother conventional configuration features may be eliminated. Theaddition or subtraction of smart lockers may automatically be detected,assigned an ID (or an ID may be deleted if a locker is removed), andupdate any data structures to reflect a change in the configuration of alocker bank. In automatically identifying new or removed lockers, eachof the lockers may have its own unique ID and/or network address thatmay be programmed during manufacturing, and the unique ID and/or networkaddress can be identified by a mobile kiosk or provisioned duringinstallation and stored by a management server.

Moreover, as a result of utilizing smart lockers that are non-networkedand utilize mobile kiosks for rental and control functionality, at leastin part, securable devices in forms that are other than lockers may beutilized. As non-limiting examples, such other uses may include mobilitydevices, such as carts, wagons, scooters, bicycles, automobiles, andboats. Other non-limiting, non-mobility uses may include mailboxes,delivery boxes, rack equipment (e.g., bicycle racks with smart locks,ski racks with smart locks, etc.), doors of storage units, safes inhotel rooms, doors of short-term or long-term living quarters, and soon. The securable devices may be integrated into the various uses or beadd-on devices. The mobile kiosks may provide access to these varioussmart locks, and enable a management server to track usage of thevarious devices (e.g., mobility devices, racks).

Because the smart locks may be configured to use little power by usingone or more local (i.e., short-range) communications protocols (e.g.,Bluetooth, WiFi, RFID, NFC, etc.) and not have to communicate via along-range communications network (e.g., mobile communications network,wide area network (WAN), such as the Internet), or local communicationsnetwork on a continuous basis, power to the smart locks may be providedin the form of batteries without having power from a power grid.Rechargeable batteries and solar cells to recharge the rechargeablebatteries may be used, for example. Moreover, because the smart locksmay utilize local communications protocols and rely on mobile devices toprovide for mobile kiosks that enable users to rent and/or access thesmart locks and items (e.g., lockers, mobility devices, etc.), the smartlocks may be utilized in ways heretofore not possible. And, becausemobile kiosks may be used in conjunction with the smart locks, anoperator may be able to manage the smart locks and devices (e.g.,mobility devices) associated therewith and receive payment for rental ofthe devices on which the smart locks are securing in locations in whichpower and communications would be difficult to provide. One example ofusing smart locks includes retrofitting existing mailboxes at a postalor mailbox rental store because battery powered smart locks retrofittedonto walls of mailboxes is easy as no grid power or networking would beneeded. Other examples of retrofitting securable devices with mechanicalor “dumb” electronic locks are contemplated.

With regard to FIG. 7B, an interaction diagram of an illustrativeenvironment 700 b in which communications between the mobile kiosk,cloud management server, and electronic lock may enable a use of themobile kiosk to perform second actions (e.g., extend rental, end rental)with a rented securable device is shown. The process 700 b may start atstep 732. At step 734, the mobile kiosk and 202 a may get a site ID fromimaging a QR code or other indicia located at a set of securable devices(e.g., locker bank). The site ID may be in the form of a web address orbe any other identifier unique to a set of securable devices, such as asmart locker system, and connect with the cloud management server 210via a long-distance communications path. At step 736, the user mayperform a request to perform a second or subsequent action with therented securable device. The second action may include opening anexisting rented lock, make a decision to extend the rental, or end arental. The mobile kiosk 202 a may communicate a unique user ID and/orPIN to the cloud management server 210.

At step 738, the cloud management server 210 may search a site datarepository, such as a database, being operated by or in communicationwith the cloud management server 210, and configured to store usageinformation of smart locks that are being rented or available for rent.At step 740, the cloud management server 210 may verify the unique IDand communicate a lock ID and open code to the mobile kiosk. The lock IDmay be a unique ID associated with a smart lock, and the open code maybe a code that, when received by the smart lock, cause the smart lock tounlock. In one embodiment, the unique ID may change after eachtransaction to ensure the security of the locker. In one embodiment, theopen code may be the PIN associated with the user and previously storedby the smart lock. Alternatively, the open code may be a command thatinstructs the smart lock to unlock or open. At step 742, mobile kiosk202 a may connect to the smart lock 206 a via a local or short-rangecommunications path, and communicate the lock ID unique to the smartlock 206 a and action command, in this case open or unlock.

At step 744, the smart lock 206 a may unlock or open the lock 206 a, andgenerate an updated lock status (e.g., unlock). At step 746, the smartlock 206 a may be closed and locked, and a communication of the rentalstatus may be made back to the mobile kiosk 202 a via the localcommunications path. At step 748, the lock status may be communicatedfrom the mobile kiosk 202 a to the cloud management server 210, which,in response, may update the status of the smart lock 206 a in a datarepository at step 750. In one embodiment, each time the smart lock 206a is engaged or performs an action, the smart lock 206 a may communicatea status update to the mobile kiosk 202 a to cause the mobile kiosk 202a (i) to update data records being stored thereby and (ii) tocommunicate the status update to the cloud management server 210 forupdating records being managed thereby.

With regard to FIGS. 8A-8C, screenshots of illustrative user interfacesthat support processes for new rental, extend rental, and end rentalprocesses of securable devices, respectively, are shown. Thesescreenshots and processes provide for rental of lockers, but it shouldbe understood that these screenshots and processes may be configured torent or access any other type of securable device, such as mobilitydevices, mailboxes, delivery boxes, mobility devices, and so forth.

With regard to FIG. 8A, an illustration that includes a number of userinterfaces for supporting a new rental process 800 a is shown. Thescreen shots and new rental process 800 a may start at an initialselection screen shown as user interface 802 on which a “new rental”soft-button 804 and “active rental” soft-button 806 are presented to auser of a mobile kiosk. In response to the user selecting the “newrental” soft-button 804, the process continues at screenshot (step) 808that presents terms and conditions 810 to the user so that the user ispresented with requirements for renting a securable device, in this casea locker. If the user does not agree with the terms and conditions 810,the user may select a “back” soft-button 812 to return to the initialselection screen 802. Alternatively, if the user accepts the terms andconditions 810, the user may select an “accept” soft-button 814. Inresponse to the user selecting the soft-button 814, the processcontinues at user interface 816 in which the user is presented with afield 818 in which a PIN may be displayed in response to the userentering a PIN on a soft-keypad 820 that may be displayed on atouchscreen or use a physical keypad if the user has a mobile deviceinclusive of a physical keypad. The PIN may be a 4-digit or other lengthPIN that the user creates. Alternatively, the mobile kiosk or managementserver may create a PIN for the user.

After the user enters his or her PIN (or a PIN is created for the user),the user may select a “next” soft-button 822, which causes the userinterface 816 to transition to user interface 824 that requests paymentfrom the user. If the user is using a mobile kiosk configured on his orher mobile device (e.g., smart phone), then the user may type a bankcard(e.g., credit card) number, expiration date, and, optionally, securitycode into another user interface (not shown) into the user interface orotherwise access payment information on his or her mobile device fromwhich the mobile kiosk may access the payment information forconfirmation. Alternative forms of payment may be utilized, aspreviously described. Screenshot 826 may present information indicativeof the mobile kiosk confirming payment. In one embodiment, the mobilekiosk confirms payment with a management server located on acommunications network, as previously described, that performs a creditcard, debit card, or other payment type transaction.

Upon completion and success of payment, the user interface 828 mayindicate that rental has started for the user. In one embodiment, if asecurable device is selected for the user by a management server ormobile kiosk, then an identifier of the securable device that wasselected for the user may be displayed in the user interface 828. In oneembodiment, an illumination device may be illuminated and/or an audibledevice may be engaged to produce an sound or otherwise indicate to auser which securable device to engage. In an alternative embodiment, theuser may proceed to a set of securable devices, and enter his or her PINinto one of the securable devices, which may cause the securable deviceto communicate with the mobile kiosk via a local communications path tocommunicate a unique identifier associated with the selected securabledevice (e.g., network address) along with the PIN, so that the mobilekiosk and management server may associate the PIN and rented securabledevice for management of the securable device. The user may select a“next” soft-button 829 to cause the mobile kiosk to display userinterface 830 that instructs the user provides locking instructions forthe user.

With regard to FIG. 8B, an illustration that includes a number of userinterfaces for supporting an extend rental process 800 b is shown. Thescreenshots and extend rental process 800 b is shown to include thescreenshot 802 that provides for the “new rental” soft-button 804 and“active rental” soft-button 806. To extend a current locker rental, theuser selects the “active rental” soft-button 806. In response,screenshot 816 is shown, where the user may enter his or her PIN intothe keypad 820. If a determination that the PIN is not found by a cloudmanagement server or the mobile kiosk, then the process 800 b maydisplay user interface 832 to provide a message 834 that the PIN was notrecognized along with other information for assistance by an operator. A“back” soft-button 836 may be presented for the user to select to returnback to user interface 816. If the PIN is recognized, then the process800 b may continue and display user interface 838, where a message 840may notify the user that he or she may (i) continue with the rental oraccess a locker or other securable device currently being rented, or(ii) end the rental and close a session out. If the user decides toextend the current rental, then the user may select an “extend”soft-button 842. Otherwise, if the user decides to end his or hercurrent rental session, then the user may select an “end” soft-button844. As shown, the user has decided to extend the rental, and theprocess 800 b continues and displays screenshot 846. The screenshot 846may provide instructions 847 to the user to indicate that he or she mayaccess the locker while the rental is extended. A “more” soft-button 848may be presented for the user to select, and, responsive to the userselecting soft-button 848, a user interface 850 that provides extensioninstructions for interfacing with the securable device may be displayedfor the user.

With regard to FIG. 8C, an illustration that includes a number of userinterfaces for supporting a new rental process 800 c is shown. Theprocess 800 c starts by presenting user interface 802, where the usermay select the “active rental” soft-button 806. In response, the mobilekiosk may display user interface 816. In response to the user entering acorrect PIN, the process 800 c displays user interface 838. In responseto the user electing to end his or her rental session, the user mayselect the “end” soft-button 844, which, in response, causes the mobilekiosk to display user interface 852 for final payment. The userinterface 852 displays a final payment amount 854 that may include anyoverage from an initial rental fee for the securable device. In thiscase, the final payment amount 854 is shown as $1.00. The user is alsopresented with a “back” soft-button 856 and “next” soft-button 858. Ifthe user selects the “back” soft-button 856, then the process returns tothe previous user interface 838. In response the user selecting “next”soft-button 858, the process continues by displaying user interface 860that notifies the user that the rental has ended. A “next” soft-button862 may be presented, and, responsive to the user selecting thesoft-button 862, user interface 864 may be displayed for the user withunlocking instructions along with a reminder message may be displayedfor the user to remove all of his or her belongings from the locker. Itshould be understood that alternative instructions may be provided ifthe securable device is not a locker.

With regard to FIGS. 9A-9C, screenshots of illustrative user interfaces900 a-900 c that are particular for renting mobility devices utilizing amobile kiosk are shown. In one embodiment, because it is possible thatthe user may want to determine whether mobility devices are availableprior to traveling to a location at which the mobility devices areavailable for rent, especially for people who have walking disabilities,the mobile kiosk may provide for rental and/or reserving a mobilitydevice prior to visiting a location at which the mobility devices arepositioned. The mobility devices may include strollers for infants,wheel chairs, electronic carts, skate boards, bicycles, and otherunpowered and powered vehicles, as understood in the art. As shown inFIG. 9A, the user interface 900 a provides three soft-buttons, a “Rent AMobility Device” soft-button 902, “Get My Reserved Mobility Device”soft-button 904, and “Manage my Existing Rental” soft-button 906.

In response to a user selecting the soft-button 902 to rent a mobilitydevice, user interface 900 b of FIG. 9B may be displayed. The userinterface 900 b shows three illustrative mobility devices, includingstrollers, wheelchairs, and electric cards with associated soft-buttons908, 910, and 912 that a user may select by tapping or otherwiseselecting on his or her mobile device. In response to the user selectingone of the mobility devices, if a mobility device of the type selected,then the user may select a “Finish and Pay” soft-button 914 that bringsthe user to a user interface that enables the user to enter bank cardinformation, as previously described. If the user is local to themobility devices that are being locked by smart locks, then the mobilekiosk being executed by a mobile device of a user may communicate withthe smart lock using a local communications path to communicate a codeassociated with a particular smart lock that is securing the selectedmobility device and PIN that may be used to lock and unlock the smartlock. However, if a determination is made by the mobile kiosk ormanagement server that no mobility devices of that type are currentlyavailable, the user interface 900 c may be presented to notify the userthat the type of mobility device selected is not available, and enablethe user (i) to find another mobility device at a different location orbe placed into a queue to put a hold on a next available device at thecurrent location by selecting soft-button 916, (ii) select a differentmobility device by selecting soft-button 918, or (iii) cancel requestinga mobility device by selecting soft-button 920.

If the user selects soft-button 916, then a search user interface (notshown) may be displayed to present the user with a list of alternativelocations at which the desired mobility device is available or enablethe user to be added to a queue or reservation list for a next availablemobility device. As an example, in the case of renting a bicycle in acity, there may be a number of locations within the city at whichbicycles available for rent or use (if part of a membership or othergroup that allows for anytime usage). A bicycle that meets the criteriaselected by the user that is available at one or more other locationsmay be displayed in a list or other format, and the user may be able torent or reserve one of the bicycles at the other location. In the caseof the user adding his or her name to a queue, the user may be providedwith a queue number along with an estimated time based on amounts oftime that others have rented the bicycles or other mobility devices or auser may be contacted via text or email when the desired device becomesavailable.

In one embodiment, the mobile kiosk may use global position system (GPS)or other geographic location capabilities of a mobile device todetermine geographic location of the mobile kiosk. The mobile kiosk maycommunicate the geographic coordinates to the management server or othercomputing system, and a determination may be made by the managementserver or other computing system what securable devices are local to theuser of the mobile kiosk and how many of those securable devices areavailable. As an example, for mobility devices in the form of bicycles,a determination may be made that there are 6 racks of bicycles within 8square blocks from a user of a mobile kiosk, and that within each ofthose racks, there are 3 bicycles currently available. The user may beable to reserve one of the bicycles and be given a pickup deadline of 20minutes. Thereafter, the reserved bicycle may be released. By using areservation system along with a queue for mobility devices, an operatormay know to reposition or add additional mobility devices where demandexceeds supply.

In an embodiment, status information of each securable device in eachset of securable devices may be stored and tracked. As an example, thestatus information may provide for a duration of time that eachsecurable device is being rented and an amount of time that remains foreach rental. In the event that all of the securable devices in a set ofsecurable deices are being rented, the management server may determinetimes or durations of time that a next available securable device willbecome available for users who request a securable device and place theuser in a queue. The users in the queue using the mobile kiosk may becommunicated with status updates, notifications, and, optionally, a timeremaining for each of the securable devices. In one embodiment, a listinclusive of securable device IDs and remaining rental times for each ofthe securable device IDs may be communicated to a mobile kiosk of a userto view. The mobile kiosk may track the remaining times for each of thesecurable devices thereafter, and any updates (e.g., rental extension)to the securable devices, may be communicated from the management serverto the mobile kiosk of the user. In another embodiment, securable devicebanks (e.g., racks of mobility devices), total number of securabledevices at each bank, and available number of securable devices at eachbank may be provided to a mobile kiosk local (e.g., within apredetermined distance, such as 6 blocks, as established by default oras a preference by a user of a mobile kiosk) to the securable devicebanks.

TABLE II provides for a cloud management system to manage one or moresecurable device systems (1−N) and securable devices (1−M) at each ofthe securable device systems. It should be understood that the number ofsecurable device systems may vary based on type of securable devices andlocations of securable device systems (e.g., amusement park, ski slope,mailbox centers, mobility devices, urban setting, residential setting,etc.). It should also be understood that the number of securable deviceswithin each of the securable device systems may vary based on type ofsecurable devices, peak demands for securable devices in differentgeographic locations, and other factors.

TABLE II Securable Device System Management for Mobile Kiosks SecurableSecurable Securable System 1 System 2 . . . System N Securable Device 1T: 46 min T: 242 min . . . Avail Securable Device 2 Avail T: 12 min . .. Reserved; T: 9 mins . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . Securable Device M T: 8 min T: 32 min; . . . T: 125 min 1renewal Total Available 6 0; Next Avail . . . 15 12 mins Queue Length 06 . . .  0 Your Queue Spot — 3 . . . —

As shown in TABLE II, each of the securable devices that are rented orcurrently being utilized may have a time T associated therewith toindicate an amount of time remaining for rental of that securabledevice, while each of the securable devices that are currently availableare indicated as being available. If a securable device is currentlyreserved, the table shows that the securable device is currentlyreserved for a remaining amount of time T (e.g., Securable System N,Securable Device 2 is reserved for another 9 minutes). It is also shownthat securable system 2, securable device M had 1 renewal, so theremaining time of 32 minutes will complete the 1st renewal for the userof that securable device. Upon the time T running out, that securabledevice becomes released, unless renewed by the user, and available foranother user. Because the management system may operate as a centralcontroller, the management system may collect the status information ofeach of the securable devices that have been rented via the mobilekiosks and update one or more data repositories from which the data inthe table is derived.

In one embodiment, the management system may communicate the datapresented in the table associated with each of the securable devicesystems and securable devices in the securable device systems that arelocal to or requested by a user of a mobile kiosk. For example, when auser is at a securable device system that is securing bicycles usingsmart locks as described herein, the management system may communicatesome or all of the data to the mobile kiosk to allow the user to viewwhich bicycles are available, reserved, or when expected to return tobecome available. The table cannot show, however, whether any of thesecurable devices that are currently being utilized will be renewed orextended by a current user, but may indicate, as described above, that asecurable device has been extended already. Hence, the available timesare estimates. In one embodiment, a number of renewals may be limited toa certain number, such as 2 renewals per user, such that a finalavailable time may be known if the rental time has a maximum amount oftime (e.g., 2 hours). As an example, if a user rents a securable devicefor 2 hours and there are 2 maximum number of renewals, then the maximumamount of time that the user may rent the securable device is 6 hours.

Below the securable devices is a listing of various summarizedstatistics, including total securable devices available, queue lengthfor each securable system, and a user's queue spot. In one embodiment,rather than having a single queue for each of the securable devicesystems, individual securable devices may have a separate queue (notshown), thereby allowing for different types of securable devices thatare more popular than others (e.g., different types of scooters) to havea queue and treated differently than others. These statistics may becommunicated to the mobile kiosks for users to view, and, optionally,set conditions or notifications based on the statistics via the mobilekiosk (e.g., send notice 15 minutes prior to estimated release ofsecurable device).

In one embodiment, the management server may be configured to providedirections and other information to users of mobile kiosks to find anavailable securable device that is within a predetermined distance oradjustable distance from a user. In one embodiment, directions may beprovided by executing a mapping app on the mobile device byautomatically inserting the starting and ending locations for the user.As an example, if all of the securable devices of a securable devicesystem (e.g., securable device system 2), then the management server maycommunicate a message to the mobile kiosk of the user in response to oras a default of a next closest securable device system (e.g., securabledevice system 1) that has available securable devices of the typedesired. In an alternative embodiment, the mobile kiosk mayautomatically request a next closest and available securable device inthe event that no securable devices are available at a local or nearestsecurable device system. In an alternative embodiment, the mobile kioskmay automatically ask the user whether he or she would like to bedirected to a currently available securable device or wait for a nextavailable securable device by being added to a queue at the closestsecurable device system.

In the event that the user is added to a queue for a securable device,notifications of when a securable device will be available for the usermay be communicated to the user. Because it is possible that theavailability may not actually occur in the event that the current userof the securable device extends or does not return the securable device,the notices may indicate that a securable is “estimated to be available”at a certain time, along with notifying the user as to his or herposition in the queue. The mobile kiosk may also be configured to enablethe user to remove him or herself from the queue, which, in turn,updates the management server to update and notify other users in thequeue.

Synchronization of the management server and mobile kiosks may use apush or pull system that either pushes status updates or pulls statusupdates to or from the mobile kiosk. The synchronization may beperformed periodically (e.g., once per minute) or aperiodically (e.g.,event triggered, such as in response to a user of a mobile kioskrequesting an update or a user returning a securable device). Acombination of periodic and aperiodic synchronization of the informationfor securable devices may also be performed.

The previous detailed description is of a small number of embodimentsfor implementing the invention and is not intended to be limiting inscope. One of skill in this art will immediately envisage the methodsand variations used to implement this invention in other areas thanthose described in detail. The following claims set forth a number ofthe embodiments of the invention disclosed with greater particularity.

What is claimed:
 1. A method of controlling a securable device in a setof securable devices, said method comprising: establishing a centralizeddata repository with data representative of status of each securabledevice in the set of securable devices; establishing communications witha mobile kiosk application executing on a mobile device of a user;responsive to receiving a request from the mobile kiosk to identify anavailable securable device local and accessible to the user: accessingthe centralized data repository; identifying at least one securabledevice that is available; and communicating data associated with theidentified at least one available securable device to the mobile kioskto cause the mobile kiosk to communicate at least a portion of the datato one of the at least one securable devices to enable the user toaccess the securable device; and responsive to receiving a status updateof the securable device accessed by the user from the mobile kiosk,updating the centralized data repository with the status update of theassociated securable device.
 2. The method according to claim 1, whereincausing the mobile kiosk to communicate at least a portion of the dataincludes causing the mobile kiosk to communicate with the securabledevice via a local communications protocol.
 3. The method according toclaim 1, wherein receiving a request from the mobile kiosk includesreceiving an identifier associated with the set of securable devices. 4.The method according to claim 1, wherein establishing a centralized datarepository includes establishing a centralized data repository withstatus data indicative of an enclosure of the securable devices beinglocked or unlocked.
 5. The method according to claim 1, whereinreceiving the request further comprises: receiving a request to rent anavailable securable device for a predetermined period of time; receivingpayment information associated with the user; performing a paymenttransaction using the payment information for the predetermined periodof time; and responsive to completion of the payment transaction,communicating the data associated with the available securable device tothe mobile kiosk.
 6. The method according to claim 1, furthercomprising: determining that each of the securable devices local to theuser are unavailable; adding the user to a queue inclusive of userswaiting for a securable device; determining, based on status informationstored in the centralized data repository, an estimated time that asecurable device will be available for the user based on a position ofthe user in the queue; and communicating the estimated time that asecurable device will be available to the mobile kiosk of the user. 7.The method according to claim 1, further comprising, responsive toupdating the centralized data repository with the status update of theassociated securable device, communicating the status update to othermobile kiosks.
 8. The method according to claim 1, wherein receiving therequest includes receiving a request with a type of securable devicedesired; and wherein identifying at least one securable device that isavailable includes identifying at least one securable device of the typerequested
 9. The method according to claim 1, wherein receiving arequest from the mobile kiosk to access a securable device includesreceiving a request from the mobile kiosk to access a securable devicethat is securing a mobility device.
 10. The method according to claim 1,further comprising, in response to determining that each of thesecurable devices local to the user are unavailable, adding the user toa queue inclusive of users waiting for a securable device; and inresponse to a securable device becoming available, communicating anotice to the user of the availability of the securable device.
 11. Themethod according to claim 10, further comprising, successivelycommunicating the notice to users waiting for a securable device in thequeue.
 12. The method according to claim 1, further comprising receivinga reservation request from the user for one of the securable devices.13. The method according to claim 12, wherein receiving a reservationrequest from the user includes receiving a reservation request from theuser via the mobile kiosk.
 14. A mobile kiosk, comprising:machine-readable instructions configured to execute on a mobile device,and, when the machine-readable instructions are executed by the mobiledevice, cause the mobile device to: communicate a request via along-distance communications path to a management server, the requestincluding an identifier associated with a plurality of securabledevices; responsive to one of the securable devices being assigned to auser of the mobile kiosk, communicate a control signal via a localcommunications path with the assigned securable device, the controlsignal causing the securable device to transition from a locked state toan unlocked state; and responsive to receiving a status update from thesecurable device via the local communications path of the securabledevice transitioning from the locked state to the unlocked state,communicating, via the long-distance communications path to themanagement server, the status update of the securable device.
 15. Themobile kiosk according to claim 14, wherein the machine-readableinstructions, when executed by the mobile device, are further configuredto enable a user to enter payment information for renting the securabledevice.
 16. The mobile kiosk according to claim 14, wherein themachine-readable instructions, when executed by the mobile device, arefurther configured to enable a user to enter a type of securable devicethe user wants to rent and amount of time that the user wants to rentthe securable device.
 17. The mobile kiosk according to claim 14,wherein the securable device is a locker or room safe.
 18. The mobilekiosk according to claim 14, wherein the securable device is a mobilitydevice or other device secured by a smart lock.
 19. The mobile kioskaccording to claim 14, wherein the machine-readable instructions, whenexecuted by the mobile device, are further configured to displayinformation indicative of an estimate amount of time that the user hasprior to a securable device becoming available.
 20. The mobile kioskaccording to claim 14, wherein the machine-readable instructions, whenexecuted by the mobile device, are further configured to display statusinformation of each of the securable devices local to the mobile kiosk.21. The mobile kiosk according to claim 14, wherein the machine-readableinstructions, when executed by the mobile device, are further configuredto: add the user to a queue inclusive of users waiting for a securabledevice in response to determining that each of the securable deviceslocal to the user are unavailable; and provide a notice to the user ofthe availability of the securable device in response to a securabledevice becoming available.
 22. The mobile kiosk according to claim 21,wherein the machine-readable instructions, when executed by the mobiledevice, are further configured to receive a communicating including anotice to the user based on a position in the queue.
 23. The mobilekiosk according to claim 14, wherein the machine-readable instructions,when executed by the mobile device, are further configured to receive areservation request from the user for one of the securable devices. 25.A method of controlling an electromechanical lock that is electronicallycontrolled, comprising: establishing, by a communications deviceassociated with the electromechanical lock, a local communications linkwith a mobile device, the electromechanical lock being responsive to acontrol signal including a network identifier; responsive to receiving acontrol signal via the local communications path, the control signalcausing the securable device to transition between a locked state and anunlocked state; and responsive to the electromechanical locktransitioning between the locked state and the unlocked state,communicating a status update via the local communications path of thesecurable device transitioning between the locked state and the unlockedstate.
 26. The method according to claim 25, wherein receiving a controlsignal includes receiving a control signal inclusive of the networkidentifier of the securable device.
 27. The method according to claim25, wherein communicating the status update further includescommunicating the network identifier in association with the statusupdate.
 28. The method according to claim 25, wherein the control signalincludes or is responsive to receiving a PIN of a user, and furthercomprising preventing, in responsive to a rental time expiring, acontrol signal associated with the user from causing the securabledevice to transition between the locked state and the unlocked state.